Changing ranking algorithms based on customer settings

ABSTRACT

Search term ranking algorithms can be generated and updated based on customer settings, such as where a ranking algorithm is modeled as a combination function of different ranking factors. An end user of a search system provides personalized preferences for weighted attributes, generally or for a single instance of the query. The user also can indicate the relative importance of one or more ranking factors by specifying different weights to the factors. Ranking factors can specify document attributes, such as document title, document body, document page rank, etc. Based on the attribute weights and the received user query, a ranking algorithm function will produce the relevant value for each document corresponding to the user preferences and personalization configurations.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

BACKGROUND OF THE INVENTION

Embodiments of the present invention relate to systems and methods for generating query results, as well as to information management systems for use with heterogeneous enterprise and other environments that may include relational database structured data and unstructured data stored in document images. Embodiments also relate to methods of searching secure data repositories that contain documents or other data items belonging to numerous heterogeneous enterprise environments, as well as methods of changing a customer-specified setting to rank results in a query in an enterprise search system able to crawl heterogeneous enterprise content.

Typically in an enterprise relational database, query generators are used to construct database queries which are then sent to a database for execution. A user constructs a query by an approach such as selecting items from a drop down list of items displayed on an interface. The items may represent data or documents which are to be obtained from a database or using a URL, or alternatively the items may represent operations that are to be performed on the data. Once the items have been selected, the query generator then generates a query, usually in Structured Query Language (SQL), for execution by the database.

An end user in an enterprise environment frequently searches huge databases. Information retrieval systems in such environments are traditionally judged by their precision and recall. Large databases of documents, such as the World Wide Web, contain many low quality documents. As a result, searches across these databases typically return hundreds of irrelevant or unwanted documents which camouflage the few relevant ones that meet the personalized needs of an end user. In order to improve the selectivity of the results, common techniques allow an end user to modify the search, or to provide additional search terms. These techniques are most effective in cases where the database is homogeneous and already classified into subsets, or in cases where the user is searching for well known and specific information. In other cases, however, these techniques are often not effective.

A typical enterprise has a large number of sources of data and many different types of data. In addition, some data may be connected to proprietary data networks, while other data sources may be connected to, and accessible from, public data networks, such as the Internet. More particularly, information within a single enterprise can be spread across Web pages, databases, mail servers or other collaboration software, document repositories, file servers, and desktops. As the number of documents accessible via an enterprise intranet or the Internet grows, the number of documents that match a particular query becomes unmanageable. Previous approaches for prioritizing searches have involved keyword priorities and pairs of keywords leading to some improvement although not every document matching the query is likely to be equally important from the user's perspective. A user may still be overwhelmed by an enormous number of documents returned by a search engine, unless the documents are ordered based on their relevance to the user's specific query and not merely limited to keywords or pairing of keywords. Another problem is that differing deployments in a heterogeneous enterprise environment may want to emphasize different document attributes, creating a difficult task for a user attempting to return results from such a document. Often, the results of such a search will be that the desired document hit is at the end of several pages of results.

One way to order documents is to create a page rank algorithm. Many search engines also provide a relevance ranking, which is a relative numerical estimate of the statistical likelihood that the material at a given URL will be of interest in comparison to other documents. Relevance rankings are often based on the number of times a keyword or search phrase appears in a document, its placement in the document and the size of the document. However, in the context of differing attributes for the same document in a heterogeneous enterprise environment, such relevance ranking tools do not offer an end user the desired level of configurability and customization.

Ranking functions that rank documents according to their relevance to a given search query are known, and while useful in some settings, do not allow a consistent user in a heterogeneous enterprise environment to personalize ranking results based on an end user set of preferences, either globally or for a single instance. Therefore, efforts continue in the art to develop ranking functions that provide better search results for a given search query compared to search results generated by search engines using known ranking functions. The ability to allow an enterprise end user to change ranking functions to customize the ranking of query results returned in heterogeneous enterprise environment to return personalized rankings of content for a single instance within the enterprise has remained unsolved.

Therefore it is desirable to provide a simple, intuitive, and heuristic method to allow an end user to change ranking algorithms to meet global or single instance requirements in a heterogeneous enterprise environment query, as well as to allow end users to rank search results in heterogeneous enterprise environments. It is desirable to provide a system that overcomes the above and other problems.

BRIEF SUMMARY OF THE INVENTION

Systems and methods in accordance with various embodiments of the present invention can provide for the generation and updating of ranking algorithms for queries and search results based on at least one customer setting, such as for a heterogeneous enterprise environment.

In one embodiment, a set of ranking factors is obtained that is to be applied to search results for a received user query. These ranking factors can be classified using a first classification for each ranking factor based on whether the ranking factors are default factors or custom factors. The ranking factors also can be classified using a second classification for each of the ranking factors based on whether the ranking factors depend upon the user query.

Depending upon the classifications, different attributes can be specified by the user, such as weights for each ranking factor and name information for custom ranking factors. When a user query is received, a ranking algorithm is generated that is specific for that user, and that can be specific for that user query as matching can activate various query-dependent factors. The ranking algorithm then is a combination function of the ranking factors that apply to the received query. The ranking algorithm then is applied to search results for the user query. The search results are then displayed ranked according to the user-supplied weights.

Reference to the remaining portions of the specification, including the drawings and claims, will realize other features and advantages of the present invention. Further features and advantages of the present invention, as well as the structure and operation of various embodiments of the present invention, are described in detail below with respect to the accompanying drawings. In the drawings, like reference numbers indicate identical or functionally similar elements.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a ranking algorithms change overall process.

FIG. 2 illustrates linking a combination function and query processing component of a client computer to a set of ranking factors classifications tables in a heterogeneous enterprise environment system.

FIG. 3 is a ranking factors classification hierarchy defined as both a factor that is either known or unknown to the secure enterprise search system and a factor that is either dependent or independent with respect to a global setting query or a single instance query.

FIG. 4 illustrates a further aspect of the invention defined as a query factor and the related process for modifying a target source attribute weighting factor defined by a user accordingly.

FIG. 5 illustrates a further aspect of the invention defined as a static factor and the related process for modifying a target source attribute weighting factor defined by a user accordingly.

FIG. 6 further illustrates an exemplary implementation of a static factor.

FIG. 7 illustrates a further aspect of the invention defined as a ranking factor value and the related process for classifying a weighted value based on seven classes.

FIG. 8 further illustrates an exemplary implementation of a known default ranking factor.

FIG. 9 further illustrates an exemplary implementation of unknown custom ranking factors that require an end user to define the type of ranking factor as either query factor or static factor.

FIG. 10 further illustrates a second exemplary implementation of a static factor.

FIG. 11 illustrates an enterprise search system, client interface and a query layer to execute a change ranking algorithm system.

FIG. 12 illustrates components of a computer network that can be used in accordance with one embodiment of the present invention.

FIG. 13 illustrates components of a computer network that can be used in accordance with one embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

Systems and methods in accordance with various embodiments of the present invention can overcome the aforementioned and other deficiencies in existing search approaches by providing for the changing of ranking algorithms based on at least one customer setting, globally or in a single instance of a heterogeneous enterprise environment, for example.

In one embodiment, a ranking algorithm is modeled as a combination function of different ranking factors. An end user of a search system may subscribe to a template in a query application interface by providing personalized preferences as to weighted attributes for the single instance of the query. The end user can, for example, indicate the relative importance of one or more ranking factors, such as by specifying different weights for the factors. The ranking factors in one embodiment specify document attributes, such as document title, document body, document page rank, etc. Based at least in part on the attribute weights and a query, a single instance ranking function will produce a relevant value for each document in accordance with these end user preferences and personalization configurations.

In one embodiment, a ranking algorithm utilizes ranking factors that are classified in two ways. First, ranking factors are classified based on whether the factors are known to the search system. For example, ranking factors are classified as “default” factors if those factors are known to the search system. Factors that are unknown to the search system are classified as “custom” factors. For example, “title” can be classified as a default factor which corresponds to a general attribute known to the search system. An attribute such as “category” can be classified as a custom attribute that corresponds to a special attribute that is only in effect in a system that is able to categorize documents.

Secondly, ranking factors in this embodiment are classified based on whether the effects of the ranking factors are dependent on the query. A query-dependent ranking factor can be classified as a “query” factor, while a query-independent ranking factor can classified as a “static” factor. These classification names are, or course, exemplary, and can include any other appropriate classification.

A query factor then will become effective only when a particular query matches the corresponding attribute. For example, a query factor will become active if terms in a user query match a value of at least one query dependent ranking factor in a candidate document. If the query factor is active, that query factor will be used to modify document attribute weighting factors, which will affect the ranking of displayed query results.

In one embodiment, a static factor will always be effective. The importance of a static factor to the ranking function, however, will be based on the value of the corresponding document attribute. For example, each document can be given a static value from “VERY GOOD” or “GOOD” to “POOR” based on “writing quality”. In this case, the name of static factor is ‘writing quality’ and it has three values: “VERY GOOD”, “GOOD”, and “POOR”. Each value will correspond to a different weight based on the individual single instance preferences of the end user. Based on the value of a document writing quality, the document will be treated differently in the ranking function algorithm according to the end user weight value assigned to “writing quality”.

In one embodiment, ranking factor weights are assigned into seven classes. A class value can be (empty): using default weight; NONE: wherein the system will not use this factor in ranking query; VERY HIGH; HIGH; MEDIUM; LOW; or VERY LOW. When the values are from “VERY LOW” to “VERY HIGH”, the corresponding ranking factor will be considered by the ranking function in a measured importance varying from very low to very high.

According to another aspect of the present invention, known default ranking factors only require an end user to specify ranking factor name and weight. For example, in XML: “<default-factor> <name>title</name></default-factor>”.

According to another aspect of the present invention, unknown custom ranking factors require an end user to define the type of ranking factor (e.g., as a query factor or static factor). For a query factor, an end user only needs to specify ranking factor name, type, and weights. For example, in XML: “<custom-factor> <attribute-name>category</attribute-name><factor-type>QUERY_FACTOR</factor-type><weight>LOW</weight></custom-factor>.”

According to another aspect of the present invention, for a static factor an end user only needs to specify ranking factor name, type, the list of static values, and corresponding weights. For example, in XML:

<custom-factor>   <attribute-name>writing quality</attribute-name>   <factor-type>STATIC_FACTOR</factor-type>   <match><value>VERY_GOOD</value>     <weight>MEDIUM</weight></match>   <match><value>POOR</value><weight>LOW</weight></match> </custom-factor>

The ranking factor specification can be set by customers to be effective for the whole search system, or the ranking factors specification can be submitted with each query and then impact ranking function differently for each query.

FIG. 1 illustrates a method 100 for searching across an enterprise in accordance with one embodiment. In this method, documents across a heterogeneous enterprise wide system are crawled 105 initially to build up a document index. A crawler component can crawl and search a variety of sources across an enterprise, regardless of whether the sources conform to a conventional user role model. In a heterogeneous enterprise wide environment, sources may represent the same document in differing ways to highlight a plurality of attributes leading to difficulties to rank results. A user then can configure or generate a search query using various user inputs 110. When a query is received, a check can be made to determine whether there are changing ranking algorithms to be applied 120, which can allow for a more current and personalized result list than can be obtained from static queries.

If there are no end user changing ranking algorithms to apply, default ranking algorithms can be applied, such as those found in a standard Web browser, whereby unranked search results are generated and presented to the user submitting the query 121. Unranked search results can be complicated when the same document may yield different results when searched in different applications, a common problem in a heterogeneous enterprise environment. As a result, the end user can be forced to adjust keywords multiple times to revise and optimize a search or search terms 122 until the desired query search results are displayed 126. Such an approach also can result in the user rerunning the search 127, in a trial and error methodology, which is inefficient, costly and slow.

If, however, there is an active changing ranking algorithm to apply to the query, the changing ranking algorithm can be generated and/or revised using a combination function 123 as discussed elsewhere herein. The algorithm can be defined using global settings 124 or for single instance ranked results based on the user preferences 125. A result based on end user preferences is obtained from a heterogeneous enterprise environment and displayed to the user submitting the query 126. The algorithms, and thus the results, can be tuned and optimized by updating the combination function to more accurately reflect user preferences. Also, changed ranking results can be tuned and optimized for each single instance of query results displayed or via an administrator or user's global settings preferences by changing ranking algorithms utilizing user feedback to match the desired returned results from a query single instance. The results can be evaluated and, if necessary, the search can be rerun 127.

FIG. 2 shows part of a system for implementing such an approach. In order to change ranking algorithms based on a customer setting, a ranking algorithm is modeled using a combination function component 210 that utilizes different ranking factors 220, 230 in an exemplary client interface 201 of an end user computer system 200. The importance of various ranking factors may be defined by specifying different weights to the factors 221, 231. The ranking factors specify document attributes, such as document title, document body, document page rank, etc. Based on the attribute weights and query, a single instance combination ranking function 210 communicatively coupled to a query processing component 240 will produce the relevant value for each document in accordance with the end user preferences and personalization configurations stored with data 204 in the database 202 to be delivered to a server computer communicatively coupled to a heterogeneous enterprise environment. An end user of the search system may subscribe to a template in the query application component interface 241 by providing personalized preferences to weighted attributes 221, 231 for the single instance of the query communicated in the enterprise environment 270. Weighted attribute factor tables 205, 206 allow an end user to perform personalized tasks to change ranking algorithms according to end user preferences and communicate the changing ranking results to the heterogeneous enterprise environment 270.

Ranking factors may be classified in two ways. FIG. 2 illustrates a ranking factor classification system 200 comprising generally a client interface 201 and a computer system server 209. A data storage system 202 of the server is comprised of a data repository 204 and further configured with known factors tables 205 and query dependent factors tables 206 to facilitate search of structured data. The client interface 201 includes a graphical display device, a plurality of screen configurations to display query results and data, and a means of data entry. An end user can utilize the ranking factors classification system to structure data according to a plurality of changed algorithms 260 selected from an algorithm scan list 250 to rank the desired query results. The database 202 further structures factors in tables for known factors 205 and query dependent factors 206.

FIG. 3 further outlines an exemplary method to change ranking factor classifications 300 in accordance with one embodiment. First a user may classify ranking factors in a first ranking factor classification 301 as to whether it is known to the secure enterprise search system, and can apply factors that are known to the search system 302. Factors that are actually known to the secure enterprise search system are defined as default factors 312. Unknown factors to the secure enterprise search system are defined as custom factors 314, as discussed above.

In the second ranking factor classification, ranking factors are classified based on whether the effects of the ranking factors are dependent on the query, and if so query-dependent factors are applied 310. Actual query dependent ranking factors are implemented 322 and a query function executed 320, while query independent factors also can be implemented 319 and executed using a static factor function 321.

FIG. 4 illustrates an exemplary method 400 for utilizing query factors where a query factor is defined 401 that will become effective only when the query matches the corresponding attribute 410. For example, if a user selects an attribute field in the query that matches the query dependent ranking factor, a query factor becomes effective a document attribute is modified 418 using a weighting ranking factor as previously discussed. If a particular query matches the corresponding attribute, the user will modify that particular document attribute weighting factor. In other words, when a user defines a query factor, the ranking algorithm will only modify those document attributes that match the user defined query document attribute. If the query does not match the attribute 420, then various factors will not become effective and thus will not be applied, whereby all other document attributes not defined will remain unmodified 426. The resulting modified and/or unmodified document attribute query factors will be utilized to change ranking algorithms which then are utilized to result in a ranked display of query results 428.

Another exemplary method 500 for implementing a static factor 500 is illustrated in FIGS. 5 and 6. Here a static factor is implemented 510 with a selected attribute to be weighted 501 and an attribute weighting assigned that is always effective 502. The priority to the ranking function, however, will be based on the value of the corresponding document attribute, as the static factors are correlated with the corresponding attribute weighting values 520. For example, each document can be given a static value from ‘VERY GOOD’, ‘GOOD’, to ‘POOR’ based on ‘writing quality’ as illustrated in the method 600 illustrated in FIG. 6. In this case, the user can define ranking criteria for corresponding static factors 601. Here the name of static factor is ‘writing quality’ and it has three values: ‘VERY GOOD’, ‘GOOD’, and ‘POOR’, and these values are assigned for the writing quality attribute 603. Other single instances of the end user static factor modification may consist of additional values assigned by the user 604. Each value will correspond to a different weight based on the individual single instance preferences of the end user. Based on the value of a document writing quality, it will be treated differently in the ranking function algorithm according to the end user weight value assigned to ‘writing quality’.

According to yet another aspect of the present invention, ranking factor weights are classified into a seven class system 700 as shown in FIG. 7, including (empty) 706 which will use a default weight 762; NONE 707, where the system will not use this factor in ranking the query 772; VERY HIGH 701; HIGH 702; MEDIUM 703; LOW 704; and VERY LOW 705. When the values are from ‘VERY LOW’ to ‘VERY HIGH’, the corresponding ranking factor will be considered by the ranking function in a measured importance varying from very low to very high.

According to another aspect of the present invention, known default ranking factors only require an end user to specify ranking factor name and weight. FIG. 8 for example, illustrates how a user might implement the method with instructions in XML.

According to another aspect of the present invention, unknown custom ranking factors require an end user to define the type of ranking factor (query factor or static factor). For query factor, an end user only needs to specify ranking factor name, type and weights. For example in FIG. 9, code to illustrate how a user might implement the method is shown in XML.

According to another aspect of the present invention, for static factor, an end user needs to specify ranking factor name, type, the list of static values and corresponding weights. For example FIG. 10 illustrates how a user might implement the method in XML. The ranking factors specification can be set by customers to be effective for the whole search system, or the ranking factors specification can be submitted with each query and then impact ranking function differently for each query.

Changing ranking algorithms can be used advantageously in a secure enterprise search (SES) system. An exemplary SES system 1100 is illustrated in FIG. 11. An SES system can utilize the text index of a database 1106. In one embodiment, a database application accepts documents and generates the lists and other elements useful for text searching. An API allows a user to submit queries, such as text queries, to search documents based on, for example, keywords.

A query layer 1102 can be configured to receive queries from users, applications, entities, etc. These can be any appropriate queries, such as simple text queries entered through a search box or advanced queries. The query layer can convert a user query into the appropriate text queries, making sure security, authorization, authentication, and other aspects are addressed, such that the results are returned to the user based on what the user is allowed to access across the enterprise. In one embodiment, the query layer can communicate with a Java component 1104 to communicate with a crawler 1108 that is able to crawl various enterprise applications, enterprise documents, enterprise objects, etc. This approach can be referred to as secure enterprise search, as an Internet search or other such searches typically are done only for public documents using more rigid queries. SES can also allow for searching of public documents, but when accessing secure content SES can ensure that only authorized persons are able to retrieve that content.

A secure enterprise search (SES) system, such as the Oracle® Secure Enterprise Search product from Oracle Corporation of Redwood Shores, Calif., can provide a simple yet powerful way to search data across an enterprise. An SES system can crawl and index any content and return relevant results in a way that is familiar to users, such as is returned for typical Internet-based search results. SES also can provide a query service API, for example, that can easily be plugged into various components in order to obtain a search service for those component.

A SES system can utilize the text index of a database. In one embodiment, a database application accepts documents and generates the lists and other elements useful for text searching. An API allows a user to submit queries, such as text queries, to search documents based on, for example, keywords.

A query layer can be configured to receive queries from users, applications, entities, etc. These can be any appropriate queries, such as simple text queries entered through a search box or advanced queries. The query layer can convert a user query into the appropriate text queries, making sure security, authorization, authentication, and other aspects are addressed, such that the results are returned to the user based on what the user is allowed to access across the enterprise. This approach can be referred to as secure enterprise search, as an Internet search or other such searches typically are done only for public documents using more rigid queries. SES can also allow for searching of public documents, but when accessing secure content SES can ensure that only authorized persons are able to retrieve that content.

Exemplary Operating Environments, Components, and Technology

FIG. 12 is a block diagram illustrating components of an exemplary operating environment in which embodiments of the present invention may be implemented. The system 1200 can include one or more user computers, computing devices, or processing devices 1212, 1214, 1216, 1218, which can be used to operate a client, such as a dedicated application, web browser, etc. The user computers 1212, 1214, 1216, 1218 can be general purpose personal computers (including, merely by way of example, personal computers and/or laptop computers running a standard operating system), cell phones or PDAs (running mobile software and being Internet, e-mail, SMS, Blackberry, or other communication protocol enabled), and/or workstation computers running any of a variety of commercially-available UNIX or UNIX-like operating systems (including without limitation, the variety of GNU/Linux operating systems). These user computers 1212, 1214, 1216, 1218 may also have any of a variety of applications, including one or more development systems, database client and/or server applications, and Web browser applications. Alternatively, the user computers 1212, 1214, 1216, 1218 may be any other electronic device, such as a thin-client computer, Internet-enabled gaming system, and/or personal messaging device, capable of communicating via a network (e.g., the network 1210 described below) and/or displaying and navigating Web pages or other types of electronic documents. Although the exemplary system 1200 is shown with four user computers, any number of user computers may be supported.

In most embodiments, the system 1200 includes some type of network 1210. The network can be any type of network familiar to those skilled in the art that can support data communications using any of a variety of commercially-available protocols, including without limitation TCP/IP, SNA, IPX, AppleTalk, and the like. Merely by way of example, the network 1210 can be a local area network (“LAN”), such as an Ethernet network, a Token-Ring network and/or the like; a wide-area network; a virtual network, including without limitation a virtual private network (“VPN”); the Internet; an intranet; an extranet; a public switched telephone network (“PSTN”); an infra-red network; a wireless network (e.g., a network operating under any of the IEEE 802.11 suite of protocols, GRPS, GSM, UMTS, EDGE, 2G, 2.5G, 3G, 4G, Wimax, WiFi, CDMA 2000, WCDMA, the Bluetooth protocol known in the art, and/or any other wireless protocol); and/or any combination of these and/or other networks.

The system may also include one or more server computers 1202, 1204, 1206 which can be general purpose computers, specialized server computers (including, merely by way of example, PC servers, UNIX servers, mid-range servers, mainframe computers rack-mounted servers, etc.), server farms, server clusters, or any other appropriate arrangement and/or combination. One or more of the servers (e.g., 1206) may be dedicated to running applications, such as a business application, a Web server, application server, etc. Such servers may be used to process requests from user computers 1212, 1214, 1216, 1218. The applications can also include any number of applications for controlling access to resources of the servers 1202, 1204, 1206.

The Web server can be running an operating system including any of those discussed above, as well as any commercially-available server operating systems. The Web server can also run any of a variety of server applications and/or mid-tier applications, including HTTP servers, FTP servers, CGI servers, database servers, Java servers, business applications, and the like. The server(s) also may be one or more computers which can be capable of executing programs or scripts in response to the user computers 1212, 1214, 1216, 1218. As one example, a server may execute one or more Web applications. The Web application may be implemented as one or more scripts or programs written in any programming language, such as Java®, C, C# or C++, and/or any scripting language, such as Perl, Python, or TCL, as well as combinations of any programming/scripting languages. The server(s) may also include database servers, including without limitation those commercially available from Oracle®, Microsoft®, Sybase®, IBM® and the like, which can process requests from database clients running on a user computer 1212, 1214, 1216, 1218.

The system 1200 may also include one or more databases 1220. The database(s) 1220 may reside in a variety of locations. By way of example, a database 1220 may reside on a storage medium local to (and/or resident in) one or more of the computers 1202, 1204, 1206, 1212, 1214, 1216, 1218. Alternatively, it may be remote from any or all of the computers 1202, 1204, 1206, 1212, 1214, 1216, 1218, and/or in communication (e.g., via the network 1210) with one or more of these. In a particular set of embodiments, the database 1220 may reside in a storage-area network (“SAN”) familiar to those skilled in the art. Similarly, any necessary files for performing the functions attributed to the computers 1202, 1204, 1206, 1212, 1214, 1216, 1218 may be stored locally on the respective computer and/or remotely, as appropriate. In one set of embodiments, the database 1220 may be a relational database, such as Oracle 10 g, that is adapted to store, update, and retrieve data in response to SQL-formatted commands.

FIG. 12 illustrates an exemplary computer system 1300, in which embodiments of the present invention may be implemented. The system 1300 may be used to implement any of the computer systems described above. The computer system 1300 is shown comprising hardware elements that may be electrically coupled via a bus 1324. The hardware elements may include one or more central processing units (CPUs) 1302, one or more input devices 1304 (e.g., a mouse, a keyboard, etc.), and one or more output devices 1306 (e.g., a display device, a printer, etc.). The computer system 1300 may also include one or more storage devices 1308. By way of example, the storage device(s) 1308 can include devices such as disk drives, optical storage devices, solid-state storage device such as a random access memory (“RAM”) and/or a read-only memory (“ROM”), which can be programmable, flash-updateable and/or the like.

The computer system 1300 may additionally include a computer-readable storage media reader 1312, a communications system 1314 (e.g., a modem, a network card (wireless or wired), an infra-red communication device, etc.), and working memory 1318, which may include RAM and ROM devices as described above. In some embodiments, the computer system 1300 may also include a processing acceleration unit 1316, which can include a digital signal processor DSP, a special-purpose processor, and/or the like.

The computer-readable storage media reader 1312 can further be connected to a computer-readable storage medium 1310, together (and, optionally, in combination with storage device(s) 1308) comprehensively representing remote, local, fixed, and/or removable storage devices plus storage media for temporarily and/or more permanently containing, storing, transmitting, and retrieving computer-readable information. The communications system 1314 may permit data to be exchanged with the network and/or any other computer described above with respect to the system 1300.

The computer system 1300 may also comprise software elements, shown as being currently located within a working memory 1318, including an operating system 1320 and/or other code 1322, such as an application program (which may be a client application, Web browser, mid-tier application, RDBMS, etc.). It should be appreciated that alternate embodiments of a computer system 1300 may have numerous variations from that described above. For example, customized hardware might also be used and/or particular elements might be implemented in hardware, software (including portable software, such as applets), or both. Further, connection to other computing devices such as network input/output devices may be employed.

Storage media and computer readable media for containing code, or portions of code, can include any appropriate media known or used in the art, including storage media and communication media, such as but not limited to volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage and/or transmission of information such as computer readable instructions, data structures, program modules, or other data, including RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, data signals, data transmissions, or any other medium which can be used to store or transmit the desired information and which can be accessed by the computer. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will appreciate other ways and/or methods to implement the various embodiments.

The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. It will, however, be evident that various modifications and changes may be made thereunto without departing from the broader spirit and scope of the invention as set forth in the claims.

While the invention has been described by way of example and in terms of the specific embodiments, it is to be understood that the invention is not limited to the disclosed embodiments. To the contrary, it is intended to cover various modifications and similar arrangements as would be apparent to those skilled in the art. Therefore, the scope of the appended claims should be accorded the broadest interpretation so as to encompass all such modifications and similar arrangements. 

1. A computer-implemented method for ranking search results using user preferences, comprising: obtaining a set of ranking factors to be applied to search results for a user query; allowing the user to supply a weight for each of the set of ranking factors; for a received user query, generating a ranking algorithm that is a combination function of the ranking factors that apply to the received query and applying the ranking algorithm to search results for the query; and displaying the search results ranked according to the user-supplied weights.
 2. The method of claim 1, further comprising: using a first classification for each of the ranking factors based on whether the ranking factors are default factors or custom factors.
 3. The method of claim 2, further comprising: using a second classification for each of the ranking factors based on whether the ranking factors depend upon the user query.
 4. The method of claim 1, further comprising: crawling a heterogeneous enterprise target corpus to generate and index and executing the received user query against the index.
 5. The method of claim 1, further comprising: allowing the user to change a weight for at least one ranking factor in order to improve the ranked search results.
 6. The method of claim 3, wherein ranking factors that depend on the query are classified as query factors.
 7. The method of claim 3, wherein ranking factors are independent of the query are classified as static factors.
 8. A computer program product embedded in a computer readable medium for ranking search results using user preferences, the computer program product comprising: program code for obtaining a set of ranking factors to be applied to search results for a user query; program code for allowing the user to supply a weight for each of the set of ranking factors; program code for generating a ranking algorithm for a received user query, the ranking algorithm being a combination function of the ranking factors that apply to the received query, and applying the ranking algorithm to search results for the query; and program code for displaying the search results ranked according to the user-supplied weights.
 9. The product of claim 8, further comprising: program code for using a first classification for each of the ranking factors based on whether the ranking factors are default factors or custom factors.
 10. The product of claim 9, further comprising: program code for using a second classification for each of the ranking factors based on whether the ranking factors depend upon the user query.
 11. The product of claim 8, further comprising: program code for crawling a heterogeneous enterprise target corpus to generate and index and executing the received user query against the index.
 12. The product of claim 8, further comprising: program code for allowing the user to change a weight for at least one ranking factor in order to improve the ranked search results.
 13. The product of claim 10, wherein ranking factors that depend on the query are classified as query factors.
 14. The product of claim 10, wherein ranking factors are independent of the query are classified as static factors.
 15. A computer system for ranking search results using user preferences, the computer system including a processor for executing instructions and a data storage medium for storing the instructions, the instructions when executed by the processor causing the processor to: obtain a set of ranking factors to be applied to search results for a user query; allow the user to supply a weight for each of the set of ranking factors; generate a ranking algorithm for a received user query, the ranking algorithm being a combination function of the ranking factors that apply to the received query, and applying the ranking algorithm to search results for the query; and display the search results ranked according to the user-supplied weights.
 16. The system of claim 15, wherein the instructions when executed further cause the processor to: use a first classification for each of the ranking factors based on whether the ranking factors are default factors or custom factors.
 17. The system of claim 16, wherein the instructions when executed further cause the processor to: use a second classification for each of the ranking factors based on whether the ranking factors depend upon the user query.
 18. The system of claim 15, wherein the instructions when executed further cause the processor to: crawl a heterogeneous enterprise target corpus to generate and index and executing the received user query against the index.
 19. The system of claim 15, wherein the instructions when executed further cause the processor to: allow the user to change a weight for at least one ranking factor in order to improve the ranked search results.
 20. The system of claim 17, wherein ranking factors that depend on the query are classified as query factors.
 21. The system of claim 17, wherein ranking factors are independent of the query are classified as static factors. 